The Terminal Server does not require secure RPC communication.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-4447	5.103	SV-29108r1_rule	ECSC-1	Medium

Description
Allowing unsecure RPC communication exposes the server to man in the middle attacks and data disclosure attacks. A man in the middle attack occurs when an intruder captures packets between a client and server and modifies them before allowing the packets to be exchanged. Usually the attacker will modify the information in the packets in an attempt to cause either the client or server to reveal sensitive information.

Description

Allowing unsecure RPC communication exposes the server to man in the middle attacks and data disclosure attacks. A man in the middle attack occurs when an intruder captures packets between a client and server and modifies them before allowing the packets to be exchanged. Usually the attacker will modify the information in the packets in an attempt to cause either the client or server to reveal sensitive information.

STIG	Date
Windows 2003 Domain Controller Security Technical Implementation Guide	2014-01-07

Details

Check Text ( C-1934r1_chk )
If the following registry value doesn’t exist or its value is not set to 1, then this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\ Value Name: fEncryptRPCTraffic Type: REG_DWORD Value: 1

Fix Text (F-5938r1_fix)
Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Terminal Services -> Encryption and Security -> RPC Security Policy “Secure Server (Require Security)” to “Enabled”.